Generating collectible items based on location information

ABSTRACT

Method for generating collectible media content items based on location information starts with processor receiving location information from location sensor coupled to first client computing device. Processor causes a map interface to be displayed that includes avatar of first user at a location based on the location information and a subset of a plurality of collectible items associated with geographical coordinates. When the first client computing device is determined to be within predetermined distance from a selected collectible item, processor causes front facing camera view to be displayed on the first client computing device, causes lens corresponding to selected collectible item to be applied to the front facing camera view, and causes the image of the selected collectible item displayed on the front facing camera view to change. Lens includes image of the selected collectible item that is overlaid on front facing camera view. Other embodiments are described herein.

PRIORITY

This patent application claims the benefit of priority to U.S. Provisional Patent Application Ser. No. 62/642,945, filed on Mar. 14, 2018, which is hereby incorporated by reference herein in its entirety.

BACKGROUND

The popularity of electronic messaging, particularly instant messaging, continues to grow. Users increasingly share media content items such as electronic images and videos with each other, reflecting a global demand to communicate more visually.

With the increasing number of systems providing applications and games to users for their mobile devices, each system is presented with the challenge of providing a graphical user interface captivates the user's attention and allows him to view interesting media content items as well as to further interact the network of individuals that the user associates with on the system.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. Some embodiments are illustrated by way of example, and not limitation, in the figures of the accompanying drawings in which:

FIG. 1 is a block diagram showing an example messaging system for exchanging data (e.g., messages and associated content) over a network.

FIG. 2 is block diagram illustrating further details regarding a messaging system, according to exemplary embodiments.

FIG. 3 is a schematic diagram illustrating data which may be stored in the database of the messaging server system, according to various exemplary embodiments.

FIG. 4 is a flow diagram of an exemplary process according to various aspects of the disclosure.

FIGS. 5A-5J are screenshots illustrating the aspects of the method described in FIG. 4.

FIG. 6 is a block diagram illustrating a representative software architecture, which may be used in conjunction with various hardware architectures herein described.

FIG. 7 is a block diagram illustrating components of a machine, according to some exemplary embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative embodiments of the disclosure. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide an understanding of various embodiments of the inventive subject matter. It will be evident, however, to those skilled in the art, that embodiments of the inventive subject matter may be practiced without these specific details. In general, well-known instruction instances, protocols, structures, and techniques are not necessarily shown in detail.

Among other things, embodiments of the present disclosure improve the functionality of electronic messaging and imaging software and systems by engaging users based on location sensor information from the users' computing devices. For example, the system generates a map interface including interactive items based on a user's location. The map interface can correspond to a location proximate to the user's location. The map interface can include, for example, a map based on the location information, an avatar of the user engaged in the current activity, a status message associated with the current activity of the user, or a status message associated with a map location on the map display. Using the system, users can also generate media content for a variety of topics and shared with other users. For example, media content (e.g., images or video) can be generated and displayed on a user's computing device, as well as transmitted to other users via electronic communications, such as short message service (SMS) or multimedia service (MMS) texts and emails.

FIG. 1 is a block diagram showing an example of a messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple client devices 102, each of which hosts a number of applications including a messaging client application 104. Each messaging client application 104 is communicatively coupled to other instances of the messaging client application 104 and a messaging server system 108 via a network 106 (e.g., the Internet). As used herein, the term “client device” may refer to any machine that interfaces to a communications network (such as network 106) to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, desktop computer, laptop, portable digital assistants (PDAs), smart phones, tablets, ultra books, netbooks, laptops, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user may use to access a network.

In the example shown in FIG. 1, each messaging client application 104 is able to communicate and exchange data with another messaging client application 104 and with the messaging server system 108 via the network 106. The data exchanged between messaging client applications 104, and between a messaging client application 104 and the messaging server system 108, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).

The network 106 may include, or operate in conjunction with, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, a network or a portion of a network may include a wireless or cellular network and the coupling may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standard, others defined by various standard setting organizations, other long range protocols, or other data transfer technology.

The messaging server system 108 provides server-side functionality via the network 106 to a particular messaging client application 104. While certain functions of the messaging system 100 are described herein as being performed by either a messaging client application 104 or by the messaging server system 108, it will be appreciated that the location of certain functionality either within the messaging client application 104 or the messaging server system 108 is a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the messaging server system 108, but to later migrate this technology and functionality to the messaging client application 104 where a client device 102 has a sufficient processing capacity.

The messaging server system 108 supports various services and operations that are provided to the messaging client application 104. Such operations include transmitting data to, receiving data from, and processing data generated by the messaging client application 104. This data may include, message content, client device information, geolocation information, media annotation and overlays, message content persistence conditions, social network information, and live event information, as examples. Data exchanges within the messaging system 100 are invoked and controlled through functions available via user interfaces (UIs) of the messaging client application 104.

Turning now specifically to the messaging server system 108, an Application Program Interface (API) server 110 is coupled to, and provides a programmatic interface to, an application server 112. The application server 112 is communicatively coupled to a database server 118, which facilitates access to a database 120 in which is stored data associated with messages processed by the application server 112.

Dealing specifically with the Application Program Interface (API) server 110, this server receives and transmits message data (e.g., commands and message payloads) between the client device 102 and the application server 112. Specifically, the Application Program Interface (API) server 110 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client application 104 in order to invoke functionality of the application server 112. The Application Program Interface (API) server 110 exposes various functions supported by the application server 112, including account registration, login functionality, the sending of messages, via the application server 112, from a particular messaging client application 104 to another messaging client application 104, the sending of electronic media files (e.g., electronic images or video) from a messaging client application 104 to the messaging server application 114, and for possible access by another messaging client application 104, the setting of a collection of media data (e.g., story), the retrieval of a list of friends of a user of a client device 102, the retrieval of such collections, the retrieval of messages and content, the adding and deletion of friends to a social graph, the location of friends within a social graph, opening and application event (e.g., relating to the messaging client application 104).

The application server 112 hosts a number of applications and subsystems, including a messaging server application 114, an image processing system 116 and a social network system 122. The messaging server application 114 implements a number of message processing technologies and functions, particularly related to the aggregation and other processing of content (e.g., textual and multimedia content including images and video clips) included in messages received from multiple instances of the messaging client application 104. As will be described in further detail, the text and media content from multiple sources may be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available, by the messaging server application 114, to the messaging client application 104. Other processor and memory intensive processing of data may also be performed server-side by the messaging server application 114, in view of the hardware requirements for such processing.

The application server 112 also includes an image processing system 116 that is dedicated to performing various image processing operations, typically with respect to electronic images or video received within the payload of a message at the messaging server application 114.

The social network system 122 supports various social networking functions services, and makes these functions and services available to the messaging server application 114. To this end, the social network system 122 maintains and accesses an entity graph 304 within the database 120. Examples of functions and services supported by the social network system 122 include the identification of other users of the messaging system 100 with which a particular user has relationships or is “following”, and also the identification of other entities and interests of a particular user.

The application server 112 is communicatively coupled to a database server 118, which facilitates access to a database 120 in which is stored data associated with messages processed by the messaging server application 114.

Some embodiments may include one or more wearable devices, such as a pendant with an integrated camera that is integrated with, in communication with, or coupled to, a client device 102. Any desired wearable device may be used in conjunction with the embodiments of the present disclosure, such as a watch, eyeglasses, goggles, a headset, a wristband, earbuds, clothing (such as a hat or jacket with integrated electronics), a clip-on electronic device, or any other wearable devices.

FIG. 2 is block diagram illustrating further details regarding the messaging system 100, according to exemplary embodiments. Specifically, the messaging system 100 is shown to comprise the messaging client application 104 and the application server 112, which in turn embody a number of some subsystems, namely an ephemeral timer system 202, a collection management system 204 and an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing the temporary access to content permitted by the messaging client application 104 and the messaging server application 114. To this end, the ephemeral timer system 202 incorporates a number of timers that, based on duration and display parameters associated with a message, or collection of messages, selectively display and enable access to messages and associated content via the messaging client application 104.

The collection management system 204 is responsible for managing collections of media (e.g., collections of text, image, video and audio data). In some examples, a collection of content (e.g., messages, including images, video, text, and audio) may be organized into an “event gallery” or an “event story.” Such a collection may be made available for a specified time period, such as the duration of an event to which the content relates. For example, content relating to a music concert may be made available as a “story” for the duration of that music concert. The collection management system 204 may also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client application 104.

The collection management system 204 furthermore includes a curation interface 208 that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface 208 enables an event organizer to curate a collection of content relating to a specific event (e.g., delete inappropriate content or redundant messages). Additionally, the collection management system 204 employs machine vision (or image recognition technology) and content rules to automatically curate a content collection. In certain embodiments, compensation may be paid to a user for inclusion of user generated content into a collection. In such cases, the curation interface 208 operates to automatically make payments to such users for the use of their content.

The annotation system 206 provides various functions that enable a user to annotate or otherwise modify or edit media content associated with a message. For example, the annotation system 206 provides functions related to the generation and publishing of media overlays for messages processed by the messaging system 100. The annotation system 206 operatively supplies a media overlay (e.g., a filter) to the messaging client application 104 based on a geolocation of the client device 102. In another example, the annotation system 206 operatively supplies a media overlay to the messaging client application 104 based on other information, such as, social network information of the user of the client device 102. A media overlay may include audio and visual content and visual effects. Examples of audio and visual content include pictures, texts, logos, animations, and sound effects. An example of a visual effect includes color overlaying. The audio and visual content or the visual effects can be applied to a media content item (e.g., an image or video) at the client device 102. For example, the media overlay including text that can be overlaid on top of a photograph/electronic image generated by the client device 102. In another example, the media overlay includes an identification of a location overlay (e.g., Venice beach), a name of a live event, or a name of a merchant overlay (e.g., Beach Coffee House). In another example, the annotation system 206 uses the geolocation of the client device 102 to identify a media overlay that includes the name of a merchant at the geolocation of the client device 102. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the database 120 and accessed through the database server 118.

In some exemplary embodiments, as discussed in more detail below, embodiments of the present disclosure may generate, display, distribute, and apply media overlays to media content items. For example, embodiments may utilize media content items generated by a client device 102 (e.g., an image or video captured using a digital camera coupled to the client device 102) to generate media overlays that can be applied to other media content items.

FIG. 3 is a schematic diagram 300 illustrating data 300 that is stored in the database 120 of the messaging server system 108, according to certain exemplary embodiments. While the content of the database 120 is shown to comprise a number of tables, the data could be stored in other types of data structures (e.g., as an object-oriented database).

The database 120 includes message data stored within a message table 314. The entity table 302 stores entity data, including an entity graph 304. Entities for which records are maintained within the entity table 302 may include individuals, corporate entities, organizations, objects, places, events etc. Regardless of type, any entity regarding which the messaging server system 108 stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).

The entity graph 304 furthermore stores information regarding relationships and associations between entities. Such relationships may be social, professional (e.g., work at a common corporation or organization) interested-based or activity-based, merely for example.

The database 120 also stores annotation data, in the example form of filters, in an annotation table 312. Filters for which data is stored within the annotation table 312 are associated with and applied to videos (for which data is stored in a video table 310) or images (for which data is stored in an image table 308). Filters, in one example, are overlays that are displayed as overlaid on an image or video during presentation to a recipient user. Filters may be of varies types, including a user-selected filters from a gallery of filters presented to a sending user by the messaging client application 104 when the sending user is composing a message.

Other types of filters include geolocation filters (also known as Geofilters) which may be presented to a sending user based on geographic location. For example, geolocation filters specific to a neighborhood or special location may be presented within a user interface by the messaging client application 104, based on geolocation information determined by a GPS unit of the client device 102. Another type of filter is a data filter, which may be selectively presented to a sending user by the messaging client application 104, based on other inputs or information gathered by the client device 102 during the message creation process. Example of data filters include current temperature at a specific location, a current speed at which a sending user is traveling, battery life for a client device 102 or the current time. Other annotation data that may be stored within the image table 308 is so-called “Lens” data. A “Lens” may be a real-time special effect and sound that may be added to an image or a video.

As mentioned above, the video table 310 stores video data which, in one embodiment, is associated with messages for which records are maintained within the message table 314. Similarly, the image table 308 stores image data associated with messages for which message data is stored in the entity table 302. The entity table 302 may associate various annotations from the annotation table 312 with various images and videos stored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages and associated image, video or audio data, which are compiled into a collection (e.g., a story or a gallery). The creation of a particular collection may be initiated by a particular user (e.g., each user for which a record is maintained in the entity table 302). A user may create a “personal story” in the form of a collection of content that has been created and sent/broadcast by that user. To this end, the user interface of the messaging client application 104 may include an icon that is user selectable to enable a sending user to add specific content to his or her personal story.

A collection may also constitute a “live story,” which is a collection of content from multiple users that is created manually, automatically or using a combination of manual and automatic techniques. For example, a “live story” may constitute a curated stream of user-submitted content from varies locations and events. Users, whose client devices have location services enabled and are at a common location event at a particular time may, for example, be presented with an option, via a user interface of the messaging client application 104, to contribute content to a particular live story. The live story may be identified to the user by the messaging client application 104, based on his or her location. The end result is a “live story” told from a community perspective.

A further type of content collection is known as a “location story,” which enables a user whose client device 102 is located within a specific geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some embodiments, a contribution to a location story may require a second degree of authentication to verify that the end user belongs to a specific organization or other entity (e.g., is a student on the university campus).

The database 120 may also stores the location of a user of a client device 102. In one embodiment, the database 120 stores a history of exact locations that the user has visited or a history of localities.

In one embodiment, the database 120 also stores the location sharing preferences set for each user. For example, the user's location sharing preferences may be set to (i) “all friends”, where all the user's friends have access to his current location; (ii) “select friends,” where the user specifically selects which of his friends are allowed access to his current location; or (iii) “ghost mode”, where no one can see his current location.

Embodiments of the present invention may generate and present customized media content items for use within electronic messages/communications such as short message service (SMS) or multimedia message service (MMS) texts and emails. The customized media content items may also be utilized in conjunction with the stories, filters, and ephemeral messaging functionality discussed herein.

The following embodiments of the invention may be described as a process, which is usually depicted as a flowchart, a flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed. A process may correspond to a method, a procedure, etc.

FIG. 4 depicts an exemplary process 400 according to various aspects of the present disclosure. The steps of method 400 may be performed in whole or in part, may be performed in conjunction each other as well as with some or all of the steps in other methods, and may be performed by any number of different systems, such as the systems described in FIGS. 1 and 7. For example, the messaging server system 108 in FIG. 1 or a processor coupled to the messaging server system 108 can perform the method 400.

In one embodiment, method 400 starts at operation 410 with the processor of system (e.g., messaging server system 108 in FIG. 1) receiving location information from a location sensor coupled to a first client computing device associated with a first user. The location information can be included in an electronic communication transmitted from the first client computing device of a user (e.g., client device 102 in FIG. 1) over a network such as the Internet (e.g., network 106 in FIG. 1). The location sensor can be, for example, position components 738 in system 700 of FIG. 7 (discussed below) that are coupled to the first client computing device. In some embodiments, the location sensor can include a global positioning sensor (GPS) component integrated in the first client computing device, as well as other types of location sensors. The processor can receive location information on a periodic basis and can request information from the user's computing device and/or receive such information from the user's device without such a request. In one exemplary embodiment, for instance, the first client computing device contains software that monitors the location sensor information from the first client computing device and transmits updates to the system in response to the location changing. In some embodiments, the first client computing device can update the system with a new location only after the location changes by at least a predetermined distance to allow a user to move about a building or other location without triggering updates.

In one embodiment, the processor can receive authorization from the first client computing device to utilize the location information and/or to display the user's avatar or location in media content items. Such authorization may be obtained via acceptance of a terms of service for utilizing an online social network or other service provided by the system, by acceptance on a case-by-case basis by the user (e.g., via popups displayed on the user's computing device) or using any other suitable method for obtaining authorization by the user(s).

At operation 420, the processor causes a map interface to be displayed by the first client computing device. The map interface can be displayed on a display screen of the first client computing device. The map interface includes a map display based on the location information and an avatar of the first user at a location on the map display based on the location information. The map display includes maps and other backgrounds.

In some embodiments, the processor updates the image of the map as the location of a user's computing device change. FIG. 5A depicts map interface that includes with an avatar of a user at his current location as well as avatars of other users in the system that are connected to the user in the system. The avatars of other users are also included in the map interface at a map location corresponding to their current location in the real world (e.g., geographical coordinates). As shown in FIG. 5A, when a number of users are located at the same location, the system may present a cluster of avatars instead of the solo avatar. In this manner, the system visually tracks the location of the user's avatar and the positions of the cluster of other avatars and other solo avatars.

The user may share media content items (e.g., via social media, text, or other electronic communication) with the respective users corresponding with other avatars, as well as with others. In this context, a “media content item” may include any type of electronic media in any format. The media content items can include a still image, animated image, video, or other content. For example, a media content item may include an image in JPG format, an image in PNG format, a video in FLV format, a video in AVI format, etc. In some exemplary embodiments, a media content item may include content that is captured using an image capture device or component (such as a digital camera) coupled to, or in communication with, a system performing the functionality of method 400. In the exemplary system 700 depicted in FIG. 7 may include a digital camera as one of input components 728. Additionally or alternatively, the media content item may be received from another system or device. In FIG. 1, for example, media content items may also include audio and combinations of different media formats (e.g., still images and video). The first user may also share (e.g., via social media, text, or other electronic communication) the display of the map interface with other users in the system. In one embodiment, the user may share the display by selecting a media content element on the display (e.g., selecting an icon or button or image to share).

As used herein, an “avatar” of a user is any visual representation of user. The avatar of a user may be based on information (e.g., characteristics) derived from images of the user in conjunction with the avatar characteristics identified from the user's relationships with other users. Alternatively or additionally, the user may select and customize characteristics of the user's avatar via the user's computing device. Such avatar characteristics may include, for example, the user's bodily features (e.g., muscular, thin, etc.), facial features, clothing and accessories, text displayed in conjunction with the avatar, and images displayed in conjunction with the avatar. The avatar information may be retrieved from a variety of sources, such as the local memory of a device performing the steps of method 400 (e.g., messaging server system 108 in FIG. 1) as well as from other systems and devices. For example, the processor can retrieve avatar information associated with the first user from a database (e.g., database 120) and generate the avatar of the first user based on the avatar information.

The map interface that is generated and caused to be displayed at operation 420 also includes a subset of a plurality of collectible items based on the location information. The collectible media content items that are shown at map locations on the map display corresponding to the geographical coordinates that have been pre-assigned to the collectible media content items. The processor can store (for example, in the database 120) the collectible items in association with a geographical coordinates that were pre-assigned to the collectible items. In one embodiment, the subset includes collectible items that are respectively associated with geographical coordinates that are included in the map display. For example, in FIG. 5A, the collectible items are illustrated as treasure hunt eggs scattered throughout the map display (e.g., West Los Angeles). Each of the eggs have been pre-assigned a geographical coordinate. The geographical coordinates may be altered by the processor as needed.

The processor may pre-assign geographical coordinates that correspond to public locations included on an approved list stored in the database of the system. For example, the approved list may include parks, malls, grassy public areas, cinemas, University or College campuses, Airport terminals, Attractions, Museums, Zoos, Train stations, Town halls, Stadiums, Post Offices, Monuments, Gazebos, Coffee Shops, Stores, Restaurants, Bars, and other places of interest. The processor may also change the pre-assigned geographical coordinates when the processor determines that the pre-assigned geographical coordinates overlap with geographical coordinates of undesirable or unsafe locations (e.g., cemeteries, elementary schools, bodies of water, highways, religious institutions, healthcare institutions, strip clubs, etc.).

At operation 430, the processor receives an input from the first client computing device selecting a selected collectible item. The selected collectible item is one of the collectible items displayed by the first client computing device's display screen. As shown in FIG. 5A, the collectible items are eggs displayed on the map interface. In order to collect or capture the egg, the user has to travel to the geographical coordinate (i.e., the physical location) of the egg on the map display. For example, the user may capture the egg in FIG. 5A that appears in Playa Vista, South of the 90 Freeway, if he travels to that location.

At operation 440, the processor determines whether the first client computing device is within a predetermined distance from geographical coordinates associated with the selected collectible item. The predetermined distance may be set by the system. In one embodiment, the predetermined distance (e.g., a collection radius) may be between 150 to 250 meters. When the processor determines that the first client computing device is not within the predetermined distance, the processor can further determine whether the first user is spoofing his location and if so, the processor can generate an alert message indicating that the first user may not collect the collectible items at his spoofed location (e.g., “We've detected that you are spoofing location. You can only collect eggs with your true location.”)

At operation 490, when the first client computing device is determined to not be within the predetermined distance, the processor causes to be displayed on the first client computing device a message prompting the user to move closer to the geographical coordinates associated with the selected collectible item. FIG. 5B illustrates a user's avatar located at Central Park in New York. The user in FIG. 5B selects the egg located at East 49^(th) Street and Lexington Avenue on the map display on his user's computing device. As shown in FIG. 5B, the processor determines that the user located at Central Park is not within the predetermined distance from the egg that he selected on the map display. The processor causes the display of the message prompting the user to move closer to the egg's location (e.g., “Too far away! Get 100 ft closer”).

When the user's computing device is determined to be within the predetermined distance, at operation 450, the processor causes a front facing camera view to be displayed on the first client computing device and at operation 460, causes a lens corresponding to the selected collectible item to be applied to the front facing camera view of the first client computing device. The lens corresponding to the selected collectible item includes an image of the selected collectible item that is overlaid on the front facing camera view. The lens can include overlays having static (i.e., non-moving) features as well as dynamic (i.e., moving) features.

FIG. 5G illustrates screenshots of five different types of collectible items. As shown in FIG. 5G, the front facing camera view of the user's computing device shows a table in an office space. In the top row of FIG. 5G, the images corresponding to the different types collectable items are different colored eggs that are overlaid on the front facing camera view. Specifically, the eggs appear to be on the table in the office space when viewed on the display of the user's computer device.

To capture or collect the egg, the first user may select the egg (e.g., tap on the screen at the location of the egg) on the display screen of the first client computing device. At operation 470, the processor receives an input from the first client computing device selecting the image of the selected collectible item on the front facing camera view. At operation 480, the processor causes the image of the selected collectible item displayed on the front facing camera view to change. The changing of the image can indicate to the first user that the selected collectible item is captured. For example, as shown in the top row of FIG. 5G, when the first user selects the egg having dots on its top half (e.g., first egg on the left), the egg may change into the clear rabbit (e.g., first rabbit on the left) in the bottom row of FIG. 5G. Similarly, when each of the eggs in the top row of FIG. 5G are selected by the first user, the eggs respectively change into the patterned rabbits below the eggs in the bottom row of FIG. 5G. FIG. 5F illustrates examples of the different rabbits associated with the different eggs that are collectible.

At operation 480, when the processor causes the image of the selected collectible item displayed on the front facing camera view to change, the processor can cause the image of the selected collectible item to be animated. FIG. 5E illustrates an example of a sequence of images in an animation of the selected collectible item.

In one embodiment, the processor can cause a score that is included on the map interface to be increased based on a number of points associated with the selected collectible item. In one embodiment, collectible items may include different types of collectible items, and each type of collectible item may be associated with a different number of points. As shown in FIG. 5A and FIG. 5G, the collectible items include eggs having different appearances (e.g., different patterns or designs thereon). In one embodiment, the different eggs are each associated with a different number of points. For example, the polka dot eggs are 10 points whereas the horizontal striped eggs and the swirl-lined eggs may be only 1 point.

In one embodiment, the processor determines a type of collectible item associated with the selected collectible item. For example, the processor determines which type of egg (e.g., polka dot egg, horizontal striped egg, etc.) is associated with the selected collectible item. The processor then determines a filter associated with the type of collectible item and provides access to the filter to the first client computing device. The filter is an overlay to a rear facing camera view displayed of the first client computing device. As shown in FIG. 5D, a different filter having different overlaid images or features may be associated for each of the types of collectible items. When the user captures or collects a collectible item, the user may be have unlocked the filter that is associated with the type of collectible item that was captured. For example, if first user captured the egg having dots on its top half (e.g., first egg on the left) in FIG. 5G, the first user is rewarded with the filter including the rabbit ears having horizontal stripes (e.g., first filter on the left in FIG. 5D). Once access is provided to the first client computing device, the first user can apply the filter to the rear facing camera view that is displayed on the first client computing device in real-time. The first user can also capture a picture taken using the rear-facing camera of the first client computing device having the filter applied thereto and share the picture with other users in the system.

The processor can cause a score associated with the first user or a number of collectible items captured by the first user to be displayed by the first client computing device. In this embodiment, the processor can cause score or number of collectible items to be displayed in association with the avatar of the user on a display screen of the user's computing device as shown in FIG. 5C. The processor can also cause the score or number of collectible items for each user in the system to be displayed in association with their respective avatars on the map display (not shown).

In one embodiment, the processor can cause a leaderboard to be displayed on the first client computing device. The leaderboard includes ranks of a plurality of users including the first user based on a score obtained by capturing collectible items. As shown in FIG. 5I, the leaderboard may be a global leaderboard that includes all the users on the system that are participating in the capture of the collectible items. In one embodiment, only non-ghost mode users (i.e., users sharing their location with the public) appear on the global leaderboard. The leaderboard, as illustrated in FIG. 5H, may also be a “friends leaderboard” which includes the user's friends (or anyone the user is associated with on the system) participating in the capture of the collectible items. In one embodiment, only the friends who are sharing location with the user appear on the “friends leaderboard.” While not shown, a localized leaderboard may also be generated that includes the users within a same locality (e.g., within a city, neighborhood, a predetermined radius of the user's location) that are participating in the capture of the collectible items. For each of the leaderboards, the user's rank is shown in comparison to the other users. As shown in FIGS. 5H and 5I, the leaderboard may also include a top three users' avatars illustrated on a podium. In FIG. 5J, another embodiment of the global leaderboard is illustrated. The global leaderboard may display, for example, the user's current rank, his percentile rank (e.g., “You're in the top 20% of all egg hunters”), and the number of eggs or points needed to increase his percentile rank (e.g., “Collect 7 ore eggs to move into the top 15% of egg hunters”).

In some embodiments, the user may access the leaderboards by selecting the first user's score, as shown in the FIG. 5B at the top right of the display, as an egg with a score (e.g., x9). The duration of the game (i.e., or the duration of the system generating collectible items for users to capture) may be limited. In this embodiment, the leaderboard may also include a timer indicating the time remaining in the game, as shown in the top right of the displays in FIGS. 5H, 5I, and 5J.

In one embodiment, the user may also share, for example, his score and position on the leaderboard with the other users in the system (e.g., selecting an icon or button or image to share).

Embodiments of the present disclosure may transmit and receive electronic communications containing media content items, media overlays, or other content any form of electronic communication, such as SMS texts, MMS texts, emails, and other communications. Media content items included in such communications may be provided as attachments, displayed inline in the message, within media overlays, or conveyed in any other suitable manner.

Software Architecture

FIG. 6 is a block diagram illustrating an exemplary software architecture 606, which may be used in conjunction with various hardware architectures herein described. FIG. 6 is a non-limiting example of a software architecture and it will be appreciated that many other architectures may be implemented to facilitate the functionality described herein. The software architecture 606 may execute on hardware such as machine 700 of FIG. 7 that includes, among other things, processors 704, memory 714, and I/O components 718. A representative hardware layer 652 is illustrated and can represent, for example, the machine 700 of FIG. 7. The representative hardware layer 652 includes a processing unit 654 having associated executable instructions 604. Executable instructions 604 represent the executable instructions of the software architecture 606, including implementation of the methods, components and so forth described herein. The hardware layer 652 also includes memory or storage modules memory/storage 656, which also have executable instructions 604. The hardware layer 652 may also comprise other hardware 658.

As used herein, the term “component” may refer to a device, physical entity or logic having boundaries defined by function or subroutine calls, branch points, application program interfaces (APIs), or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions.

Components may constitute either software components (e.g., code embodied on a machine-readable medium) or hardware components. A “hardware component” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various exemplary embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware components of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations as described herein. A hardware component may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic that is permanently configured to perform certain operations.

A hardware component may be a special-purpose processor, such as a Field-Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). A hardware component may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware components become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware component mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

A processor may be, or in include, any circuit or virtual circuit (a physical circuit emulated by logic executing on an actual processor) that manipulates data values according to control signals (e.g., “commands”, “op codes”, “machine code”, etc.) and which produces corresponding output signals that are applied to operate a machine. A processor may, for example, be a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC) or any combination thereof. A processor may further be a multi-core processor having two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously.

Accordingly, the phrase “hardware component” (or “hardware-implemented component”) should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time. Hardware components can provide information to, and receive information from, other hardware components. Accordingly, the described hardware components may be regarded as being communicatively coupled. Where multiple hardware components exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware components. In embodiments in which multiple hardware components are configured or instantiated at different times, communications between such hardware components may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware components have access.

For example, one hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware component may then, at a later time, access the memory device to retrieve and process the stored output. Hardware components may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information). The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented component” refers to a hardware component implemented using one or more processors. Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented components.

Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an Application Program Interface (API)). The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some exemplary embodiments, the processors or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other exemplary embodiments, the processors or processor-implemented components may be distributed across a number of geographic locations.

In the exemplary architecture of FIG. 6, the software architecture 606 may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture 606 may include layers such as an operating system 602, libraries 620, applications 616 and a presentation layer 614. Operationally, the applications 616 or other components within the layers may invoke application programming interface (API) API calls 608 through the software stack and receive messages 612 in response to the API calls 608. The layers illustrated are representative in nature and not all software architectures have all layers. For example, some mobile or special purpose operating systems may not provide a frameworks/middleware 618, while others may provide such a layer. Other software architectures may include additional or different layers.

The operating system 602 may manage hardware resources and provide common services. The operating system 602 may include, for example, a kernel 622, services 624 and drivers 626. The kernel 622 may act as an abstraction layer between the hardware and the other software layers. For example, the kernel 622 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The services 624 may provide other common services for the other software layers. The drivers 626 are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 626 include display drivers, camera drivers, Bluetooth® drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and so forth depending on the hardware configuration.

The libraries 620 provide a common infrastructure that is used by the applications 616 or other components or layers. The libraries 620 provide functionality that allows other software components to perform tasks in an easier fashion than to interface directly with the underlying operating system 602 functionality (e.g., kernel 622, services 624 or drivers 626). The libraries 620 may include system libraries 644 (e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematical functions, and the like. In addition, the libraries 620 may include API libraries 646 such as media libraries (e.g., libraries to support presentation and manipulation of various media format such as MPREG4, H.264, MP3, AAC, AMR, JPG, PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D in a graphic content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. The libraries 620 may also include a wide variety of other libraries 648 to provide many other APIs to the applications 616 and other software components/modules.

The frameworks/middleware 618 (also sometimes referred to as middleware) provide a higher-level common infrastructure that may be used by the applications 616 or other software components/modules. For example, the frameworks/middleware 618 may provide various graphic user interface (GUI) functions, high-level resource management, high-level location services, and so forth. The frameworks/middleware 618 may provide a broad spectrum of other APIs that may be utilized by the applications 616 or other software components/modules, some of which may be specific to a particular operating system 602 or platform.

The applications 616 include built-in applications 638 or third-party applications 640. Examples of representative built-in applications 638 may include, but are not limited to, a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, or a game application. Third-party applications 640 may include an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform, and may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. The third-party applications 640 may invoke the API calls 608 provided by the mobile operating system (such as operating system 602) to facilitate functionality described herein.

The applications 616 may use built in operating system functions (e.g., kernel 622, services 624 or drivers 626), libraries 620, and frameworks/middleware 618 to create user interfaces to interact with users of the system. Alternatively, or additionally, in some systems interactions with a user may occur through a presentation layer, such as presentation layer 614. In these systems, the application/component “logic” can be separated from the aspects of the application/component that interact with a user.

FIG. 7 is a block diagram illustrating components (also referred to herein as “modules”) of a machine 700, according to some exemplary embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 7 shows a diagrammatic representation of the machine 700 in the example form of a computer system, within which instructions 710 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 700 to perform any one or more of the methodologies discussed herein may be executed. As such, the instructions 710 may be used to implement modules or components described herein. The instructions 710 transform the general, non-programmed machine 700 into a particular machine 700 programmed to carry out the described and illustrated functions in the manner described. In alternative embodiments, the machine 700 operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 700 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 700 may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 710, sequentially or otherwise, that specify actions to be taken by machine 700. Further, while only a single machine 700 is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions 710 to perform any one or more of the methodologies discussed herein.

The machine 700 may include processors 704, memory memory/storage 706, and I/O components 718, which may be configured to communicate with each other such as via a bus 702. The memory/storage 706 may include a memory 714, such as a main memory, or other memory storage, and a storage unit 716, both accessible to the processors 704 such as via the bus 702. The storage unit 716 and memory 714 store the instructions 710 embodying any one or more of the methodologies or functions described herein. The instructions 710 may also reside, completely or partially, within the memory 714, within the storage unit 716, within at least one of the processors 704 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 700. Accordingly, the memory 714, the storage unit 716, and the memory of processors 704 are examples of machine-readable media.

As used herein, the term “machine-readable medium,” “computer-readable medium,” or the like may refer to any component, device or other tangible media able to store instructions and data temporarily or permanently. Examples of such media may include, but is not limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., Erasable Programmable Read-Only Memory (EEPROM)) or any suitable combination thereof. The term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions. The term “machine-readable medium” may also be taken to include any medium, or combination of multiple media, that is capable of storing instructions (e.g., code) for execution by a machine, such that the instructions, when executed by one or more processors of the machine, cause the machine to perform any one or more of the methodologies described herein. Accordingly, a “machine-readable medium” may refer to a single storage apparatus or device, as well as “cloud-based” storage systems or storage networks that include multiple storage apparatus or devices. The term “machine-readable medium” excludes signals per se.

The I/O components 718 may include a wide variety of components to provide a user interface for receiving input, providing output, producing output, transmitting information, exchanging information, capturing measurements, and so on. The specific I/O components 718 that are included in the user interface of a particular machine 700 will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components 718 may include many other components that are not shown in FIG. 7. The I/O components 718 are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various exemplary embodiments, the I/O components 718 may include output components 726 and input components 728. The output components 726 may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. The input components 728 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like. The input components 728 may also include one or more image-capturing devices, such as a digital camera for generating digital images or video.

In further exemplary embodiments, the I/O components 718 may include biometric components 730, motion components 734, environmental environment components 736, or position components 738, as well as a wide array of other components. One or more of such components (or portions thereof) may collectively be referred to herein as a “sensor component” or “sensor” for collecting various data related to the machine 700, the environment of the machine 700, a user of the machine 700, or a combinations thereof.

For example, the biometric components 730 may include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram based identification), and the like. The motion components 734 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, velocity sensor components (e.g., speedometer), rotation sensor components (e.g., gyroscope), and so forth. The environment components 736 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometer that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components 738 may include location sensor components (e.g., a Global Position system (GPS) receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like. For example, the location sensor component may provide location information associated with the system 700, such as the system's 700 GPS coordinates or information regarding a location the system 700 is at currently (e.g., the name of a restaurant or other business).

Communication may be implemented using a wide variety of technologies. The I/O components 718 may include communication components 740 operable to couple the machine 700 to a network 732 or devices 720 via coupling 722 and coupling 724 respectively. For example, the communication components 740 may include a network interface component or other suitable device to interface with the network 732. In further examples, communication components 740 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices 720 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a Universal Serial Bus (USB)).

Moreover, the communication components 740 may detect identifiers or include components operable to detect identifiers. For example, the communication components 740 may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components 740, such as, location via Internet Protocol (IP) geo-location, location via Wi-Fi® signal triangulation, location via detecting a NFC beacon signal that may indicate a particular location, and so forth.

Where a phrase similar to “at least one of A, B, or C,” “at least one of A, B, and C,” “one or more A, B, or C,” or “one or more of A, B, and C” is used, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C.

Changes and modifications may be made to the disclosed embodiments without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure, as expressed in the following claims. 

What is claimed is:
 1. A method comprising: receiving, by a processor, location information from a location sensor coupled to a first client computing device, wherein the first client computing device is associated with a first user; causing a map interface to be displayed by the first client computing device, the map interface including an avatar of the first user at a location on the map display based on the location information and a subset of a plurality of collectible items based on the location information, wherein the plurality of collectible items are respectively associated with geographical coordinates, wherein the subset includes at least one of the plurality of collectible items that is respectively associated with geographical coordinates that are included in the map display; receiving an input from the first client computing device selecting a selected collectible item, wherein the selected collectible item is one of the collectible items displayed by the first client computing device; determining whether the first client computing device is within a predetermined distance from geographical coordinates associated with the selected collectible item; and when the first client computing device is determined to be within the predetermined distance, causing a front facing camera view to be displayed on the first client computing device, causing a lens corresponding to the selected collectible item to be applied to the front facing camera view of the first client computing device, wherein the lens corresponding to the selected collectible item includes an image of the selected collectible item that is overlaid on the front facing camera view, receiving an input from the first client computing device selecting the image of the selected collectible item on the front facing camera view, and causing the image of the selected collectible item displayed on the front facing camera view to change.
 2. The method of claim 1, wherein the plurality of collectible items include a plurality of types of collectible items, wherein each type of collectible item is associated with a number of points.
 3. The method of claim 2, further comprising: causing a score associated with the first user or a number of collectible items captured by the first user to be displayed by the first client computing device.
 4. The method of claim 2, further comprising: determining a type of collectible item associated with the selected collectible item; and determining a filter associated with the type of collectible item; and providing access to the filter to the first client computing device, wherein the filter is an overlay to a rear facing camera view displayed of the first client computing device.
 5. The method of claim 2, further comprising: causing a leaderboard to be displayed on the first client computing device, wherein the leaderboard includes ranks of a plurality of users including the first user based on a score obtained by capturing collectible items.
 6. The method of claim 1, further comprising: when the first client computing device is determined to not be within the predetermined distance, causing to be displayed on the first client computing device a message prompting the first user to move closer to the geographical coordinates associated with the selected collectible item.
 7. The method of claim 1, further comprising: receiving, from the first client computing device over the network, authorization from the first user to utilize the location information.
 8. The method of claim 1, further comprising: retrieving, from a database, avatar information for the first user.
 9. The method of claim 1, wherein causing the image of the selected collectible item displayed on the front facing camera view to change includes causing the image of the selected collectible item to be animated.
 10. The method of claim 1, further comprising: causing a score that is included on the map interface to be increased based on a number of points associated with the selected collectible item.
 11. A non-transitory computer-readable storage medium having stored thereon, instructions when executed by a processor, causes the processor to perform a method comprising: receiving location information from a location sensor coupled to a first client computing device, wherein the first client computing device is associated with a first user; causing a map interface to be displayed by the first client computing device, the map interface including an avatar of the first user at a location on the map display based on the location information and a subset of a plurality of collectible items based on the location information, wherein the plurality of collectible items are respectively associated with geographical coordinates, wherein the subset includes at least one of the plurality of collectible items that is respectively associated with geographical coordinates that are included in the map display; receiving an input from the first client computing device selecting a selected collectible item, wherein the selected collectible item is one of the collectible items displayed by the first client computing device; determining whether the first client computing device is within a predetermined distance from geographical coordinates associated with the selected collectible item; and when the first client computing device is determined to be within the predetermined distance, causing a front facing camera view to be displayed on the first client computing device, causing a lens corresponding to the selected collectible item to be applied to the front facing camera view of the first client computing device, wherein the lens corresponding to the selected collectible item includes an image of the selected collectible item that is overlaid on the front facing camera view, receiving an input from the first client computing device selecting the image of the selected collectible item on the front facing camera view, and causing the image of the selected collectible item displayed on the front facing camera view to change.
 12. The non-transitory computer-readable storage medium of claim 11, wherein the plurality of collectible items include a plurality of types of collectible items, wherein each type of collectible item is associated with a number of points.
 13. The non-transitory computer-readable storage medium of claim 12, wherein the processor to perform the method further comprising: causing a score associated with the first user or a number of collectible items captured by the first user to be displayed by the first client computing device.
 14. The non-transitory computer-readable storage medium of claim 12, wherein the processor to perform the method further comprising: determining a type of collectible item associated with the selected collectible item; and determining a filter associated with the type of collectible item; and providing access to the filter to the first client computing device, wherein the filter is an overlay to a rear facing camera view displayed of the first client computing device.
 15. The non-transitory computer-readable storage medium of claim 12, wherein the processor to perform the method further comprising: causing a leaderboard to be displayed on the first client computing device, wherein the leaderboard includes ranks of a plurality of users including the first user based on a score obtained by capturing collectible items.
 16. The non-transitory computer-readable storage medium of claim 11, wherein the processor to perform the method further comprising: when the first client computing device is determined to not be within the predetermined distance, causing to be displayed on the first client computing device a message prompting the first user to move closer to the geographical coordinates associated with the selected collectible item.
 17. The non-transitory computer-readable storage medium of claim 11, wherein causing the image of the selected collectible item displayed on the front facing camera view to change includes causing the image of the selected collectible item to be animated.
 18. The non-transitory computer-readable storage medium of claim 11, wherein the processor to perform the method further comprising: causing a score that is included on the map interface to be increased based on a number of points associated with the selected collectible item.
 19. A system comprising: a messaging server system including: an application server to: receive location information from a location sensor coupled to a first client computing device, wherein the first client computing device is associated with a first user; cause a map interface to be displayed by the first client computing device, the map interface including an avatar of the first user at a location on the map display based on the location information and a subset of a plurality of collectible items based on the location information, wherein the plurality of collectible items are respectively associated with geographical coordinates, wherein the subset includes at least one of the plurality of collectible items that is respectively associated with geographical coordinates that are included in the map display; receive an input from the first client computing device selecting a selected collectible item, wherein the selected collectible item is one of the collectible items displayed by the first client computing device; determine whether the first client computing device is within a predetermined distance from geographical coordinates associated with the selected collectible item; and when the first client computing device is determined to be within the predetermined distance, cause a front facing camera view to be displayed on the first client computing device, cause a lens corresponding to the selected collectible item to be applied to the front facing camera view of the first client computing device, wherein the lens corresponding to the selected collectible item includes an image of the selected collectible item that is overlaid on the front facing camera view, receive an input from the first client computing device selecting the image of the selected collectible item on the front facing camera view, and cause the image of the selected collectible item displayed on the front facing camera view to change.
 20. The system of claim 19, wherein, when the first client computing device is determined to not be within the predetermined distance, the application server further to: cause to be displayed on the first client computing device a message prompting the first user to move closer to the geographical coordinates associated with the selected collectible item. 